System and method for EUICC personalization and network provisioning

ABSTRACT

A method is provided for self-provisioning and personalization of a companion device. A primary user device receives input to initiate a cellular service activation process for a companion device, wherein the companion device includes a preloaded version of a service provider application for facilitating remote provisioning. The primary device provides, to the companion device, an updated version of the service provider application that replaces the preloaded version. The primary device receives, from the companion device, an embedded universal integrated circuit card (eUICC) identifier for the companion device and forwards the eUICC identifier to a network device and an identifier for the primary device. When the network device verifies that the cellular service activation for the companion device can be provisioned, the primary device receives an activation code for the companion device to use to initiate a request for a new line of service for the eUICC identifier and forwards the activation code to the companion device.

CROSS REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.15/475,596 filed on Mar. 31, 2017, the contents of which areincorporated herein by reference.

BACKGROUND

Today, Universal Integrated Circuit Cards (UICC), such as subscriberidentity module (SIM) cards, are individually formatted with a serviceprovider's authentication credentials, an International MobileSubscriber Identity (IMSI), an integrated circuit card identifier(ICCID), etc. in secured UICC vendor factories as part of the UICCmanufacturing process. For devices that are branded for a specificwireless service provider, the UICC is typically pre-inserted into adevice at the OEM facility or it may also be inserted at time of sale.When the user receives a device branded for the service provider, itwill have a UICC with the service provider's credentials already presentand available for activation.

Wireless device manufacturers seek to globalize their devices, such thatone make/model of a device can support all wireless carriers across theglobe and also allow consumers to have multiple subscriptions on thesame device. One key for global devices is the ability to convenientlymodify the device SIM profile to support different wireless carriers,such as in instances in which the UICC is not easily accessible or ispermanently installed into the device. Industry standards are now movingtoward dynamic personalization that provides the ability to dynamicallychange the SIM profile on an embedded UICC (eUICC) after manufacture.This dynamic personalization typically requires user input, such as toenter (or scan) a QR activation code or similar code, which can becumbersome to provide when the eUICC is used in a small form factordevice, such as a wearable device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating an exemplary network in which systemsand/or methods described herein may be implemented;

FIG. 2 is a block diagram illustrating exemplary components of a devicethat may correspond to a companion device, primary device, or a networkdevice of FIG. 1;

FIG. 3 is a diagram of functional components of the companion device ofFIG. 1;

FIG. 4 is a diagram of functional components of the primary device ofFIG. 1;

FIG. 5 is a diagram illustrating exemplary communications among networkelements in apportion of the network of FIG. 1;

FIG. 6 is a flow diagram illustrating an exemplary process forprovisioning an eUICC of a companion device for cellular activation,according to an implementation described herein;

FIGS. 7-10 are diagrams illustrating use cases relating to provisioningan eUICC of a companion device, according to implementations describedherein; and

FIG. 11 is an illustration of a use case for end-user interactionsduring a first time synchronization of a companion device with primarydevice, according to an implementation described herein.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements.

The use of cellular data service is becoming a more popular option forelectronic devices that have not traditionally included suchfunctionality, such as wearable devices including smart watches, fitnessbands, activity trackers, clip-on monitors, as well as other types ofdevices, such as vehicle-based systems (telematics or infotainmentsystems), smart appliances or other Internet of Things (IoT) devices,etc. A companion application for use on a smartphone (or other computingdevice) is sometimes made available for use in conjunction with theelectronic device. The smartphone or other computing device is referredto herein as a “primary device” or “primary user device” and theelectronic device is referred to herein as a “companion device.”

Dynamic personalization for cellular devices, as described in industrystandards, provides the ability to dynamically change the SIM profile onan eUICC after card manufacture, without physically changing devicehardware. Systems and methods described herein facilitate dynamicpersonalization and remote provisioning of the eUICC for a companiondevice. More particularly, the systems and methods described hereinsimplify the process for an end user to fully self-activate a companiondevice remotely. In one implementation, the process may be executeddirectly from the companion device that is pre-installed with apre-personalized eUICC profile. In another implementation, the processmay use a primary device as an available/paired device to providenetwork connectivity needed to activate a companion device under asubscriber billing account associated with the paired primary device andto allow for download of the required eUICC profile. Additionally, theprimary device allows for an enhanced end user experience, not only forease of activation request submission, but also to allow for review ofany errors using a more user friendly interface than can be accommodatedon the companion device.

According to one implementation, a method is provided for dynamicself-provisioning and personalization of a companion device. A primarydevice may receive, via an activation application for cellular serviceactivation of a companion device, user input to initiate a cellularservice activation process for the companion device. The primary devicemay establish a local network connection with the companion device andmay receive from the companion device an eUICC identifier. The primarydevice may forward, to a network device in a service provider network,the eUICC identifier along with an identifier for the primary userdevice. After a network device verifies that cellular service for thecompanion device can be activated under a subscriber account associatedwith the primary device, the primary device may receive, from thenetwork device, an activation code for the eUICC and may forward to thecompanion device the activation code via the local network connection.The activation code may automatically cause the companion device toinitiate a profile download request for an eUICC to be included with anew line of service under a subscriber account associated with theprimary user device.

FIG. 1 is a diagram illustrating an exemplary environment 100 in whichsystems and methods described herein may be implemented. As illustrated,environment 100 may include an access network 105, a core network 110, aservice network 120, a backhaul network 130, a companion device 140, anda primary device 150. Service network 120 may have multiple networkelements including, but not limited to, a remote personalization server(RPS) 122, a subscription manager platform 124, and a provisioningplatform 126. For purposes of description, RPS 122, subscription managerplatform 124, provisioning platform 126, companion device 140, andprimary device 150 may be referred to as network elements withinenvironment 100.

As further illustrated, environment 100 includes communicative links 160between the network elements and networks (although only four arereferenced in FIG. 1 as links 160-1, 160-2, 160-3, and 160-4). A networkelement may transmit and receive data via a link 160. Environment 100may be implemented to include wireless and/or wired (e.g., electrical,optical, etc.) links 160. A communicative connection between networkelements may be direct or indirect. For example, an indirectcommunicative connection may involve an intermediary device or networkelement, and/or an intermediary network not illustrated in FIG. 1.Additionally, the number, the type (e.g., wired, wireless, etc.), andthe arrangement of links 160 illustrated in environment 100 areexemplary.

A network element may be implemented according to a centralizedcomputing architecture, a distributed computing architecture, or a cloudcomputing architecture (e.g., an elastic cloud, a private cloud, apublic cloud, etc.). Additionally, a network element may be implementedaccording to one or multiple network architectures (e.g., a clientdevice, a server device, a peer device, a proxy device, and/or a clouddevice). The number of network elements, the number of networks, and thearrangement in environment 100 are exemplary. According to otherembodiments, environment 100 may include additional network elements,fewer network elements, and/or differently arranged network elements,than those illustrated in FIG. 1. For example, there may be numerouscompanion devices 140, primary devices 150, and so forth. In otherembodiments, one network in environment 100 may be combined with anothernetwork.

Access network 105 may include one or multiple networks of one ormultiple types. For example, access network 105 may be implemented toinclude a terrestrial network, a satellite network, a wireless network,and/or a wired network. According to an exemplary implementation, accessnetwork 105 includes a radio access network (RAN). The RAN may be aThird Generation (3G) RAN, a Fourth Generation (4G) RAN, a 5G RAN, afuture generation wireless network architecture, etc. By way of furtherexample, access network 105 may include an Evolved UMTS TerrestrialRadio Access Network (E-UTRAN) of a Long Term Evolution (LTE) network orLTE-Advanced (LTE-A) network. Depending on the implementation, accessnetwork 105 may include various network elements, such as a base station(BS), a Node B, an evolved Node B (eNB), a BS controller, a radionetwork controller (RNC), a femto device, a pico device, a home eNB, arelay node, a wireless access point, or other type of wireless node thatprovides wireless access. In aspects where access network includes aRAN, devices (e.g., companion device 140, primary device 150) mayrequire activation by a service provider to use access network 105. Inother aspects, access network 105 may include a wired network. Forexample, access network 105 may include an optical network or a cablenetwork.

Core network 110 may include one or multiple networks of one or multipletypes. For example, core network 110 may be implemented to include aterrestrial network, a satellite network, a wireless network, and/or awired network. According to an exemplary implementation, core network110 includes a complementary network pertaining to the one or multipleRANs described above. For example, core network 110 may include the corepart of an LTE network, an LTE-A network, etc. Depending on theimplementation, core network 110 may include various network elements,such as a gateway, a support node, a serving node, a router, a switch, abridge, as well other network elements pertaining to variousnetwork-related functions, such as billing, security, authentication andauthorization, network polices, subscriber profiles, etc.

Service network 120 includes one or multiple networks of one or multipletypes. For example, service network 120 may include a private IPnetwork, an Internet Protocol (IP) Multimedia Subsystem (IMS) network, acloud network, a wide area network (WAN), a metropolitan area network(MAN), the Internet, the World Wide Web, a service provider network,some other type of backend network, and so forth. As illustrated,according to an exemplary embodiment, service network 120 includes RPS122, subscription manager platform 124, and provisioning platform 126.According to other exemplary embodiments, RPS 122, subscription managerplatform 124, provisioning platform 126, and/or a portion thereof may beimplemented in another network, such as core network 110.

RPS 122 may include one or more network devices, or other types ofcomputation or communication devices, to facilitate self-servepersonalization and remote provisioning of companion device 140. In oneimplementation, RPS 122 may apply user information from service provideractivation application 420 and/or service provider application 310 toassociate companion device 140 with an account for primary device 150.RPS 122 may initiate provisioning for activation of companion device 140on the carrier network and communicate with primary device 150 toforward information (such as an activation code) to companion device140.

Subscription manager platform 124 may include one or more networkdevices, or other types of computation or communication devices, tomanage activation of cellular devices on the carrier network.Subscription manager platform 124 may receive registration data, billingdata, provisioning instructions, and other account settings for mobiledevices. Subscription manager platform 124 may communicate with networkdevices in core network 110—such as a home subscriber server(HSS)/authentication, authorization, and accounting (AAA) server, apolicy and charging rules function (PCRF) device—to assign activationcodes, unique identifiers, and authenticators for cellular devices,including companion device 140.

Provisioning platform 126 may include one or more engineering,operation, and inventory databases and systems that maintain and provideinformation relating to activating and provisioning service orders innetwork environment 100. Provisioning platform 126 may include tools forenabling entry and tracking of customer service orders and may activelytransmit information regarding the orders to other systems in networkenvironment 100, such as a billing system (not shown). In someimplementations, provisioning platform 126 may include inventoryinformation associated with all devices and equipment within environment100, including companion devices 140, primary devices, 150, cabling,wiring, network devices, etc.

Backhaul network 130 includes one or multiple networks of one ormultiple types. According to an exemplary implementation, backhaulnetwork 130 includes a backbone network. For example, the backbonenetwork may be implemented as an optical transport network or othersuitable architecture. According to one implementation, backhaul network130 provides a connection path from access network 105 to servicenetwork 120. According to another implementation, when access network105 is implemented as an LTE RAN or an LTE-A RAN, backhaul network 130may directly connect to an eNB. In some instances, access network 105,core network 110, service network 120, and backhaul network 130 may becollectively referred to as a carrier network.

Companion device 140 may include a communication and computationaldevice. For example, companion device 140 may include a smart watch, afitness tracker, or another device that may be worn or otherwise coupledto a user. In some examples, companion device 140 may take the form of awristband-mounted device (like a wristwatch) or another wearable formfactor, such as a pendant style device configured for wearing via achain or lanyard, a brooch or other pin-on or clip-on on style device,an armband-mounted device, etc. Companion device 140 may include one ormultiple applications which may be executed on companion device 140 toperform particular functions, such as communications (e.g., texts,emails, voice), information (e.g., weather, news, sports), monitoring(e.g., movements, vital signs, etc.), and other functions. According toan exemplary embodiment, companion device 140 may include acommunication interface via which companion device 140 can transmit andreceive data. For example, companion device 140 may be implemented toinclude various technologies, such as a sensor, a tag, a camera, anantenna, etc., that collect, obtain, and/or generate data. In otherimplementations, companion device 140 may include a vehicle-based system(e.g., telematics or infotainment system), a smart appliance, or anotherIoT device. In some aspects, companion device 140 may be an embeddeddevice, such as micro-controller for a tool, footwear, toy, etc.

According to an implementation, the communication interface forcompanion device 140 includes a cellular modem, such as an LTE and/or anLTE-A modem (referred to herein as an “LTE modem”). In oneimplementation, companion device 140 may transmit data to servicenetwork 120 via core network 110. According to an exemplary embodiment,companion device 140 includes a service provider application thatassists with cellular activation of companion device 140.

Primary device 150 may include a communication and computational device.Primary device 150 may be implemented as a mobile device, a portabledevice, or a stationary device. For example, primary device 150 may beimplemented as a smartphone, a tablet device, a computer (e.g., alaptop, a desktop, a palmtop, etc.), a personal digital assistant, aterminal, and so forth. In one implementation, primary device 150 mayinclude a communication interface with a cellular modem (e.g., LTEmodem) and a local wired/wireless interface (e.g., a universal serialbus (USB) port for communications over a cable, a Bluetooth® (BT)/BTEmbedded System (BTE) or BT Low Energy (BTLE) interface, a near-fieldcommunication (NFC) wireless interface, and/or a Wi-Fi interface.According to an exemplary embodiment, primary device 150 includes acompanion application for companion device 140 that assists withcellular activation of companion device 140.

Links 160 provide communication paths between network elements and/ornetworks of environment 100. Links 160 may have certain characteristics,such as bandwidth capacity, transmission data rate, and the like.

FIG. 2 is a diagram illustrating exemplary components of a device 200,according to an implementation described herein. Each of companiondevice 140 and primary device 150 may be implemented as a combination ofhardware and software on one or more of device 200. As shown in FIG. 2,device 200 may include a bus 210, a processor 220, a memory 230, aninput component 240, an output component 250, a communication interface260, and a secure element 270.

Bus 210 may include a path that permits communication among thecomponents of device 200. Processor 220 may include a processor, amicroprocessor, or processing logic that may interpret and executeinstructions. Memory 230 may include any type of dynamic storage devicethat may store information and instructions, for execution by processor220, and/or any type of non-volatile storage device that may storeinformation for use by processor 220.

Software 235 includes an application or a program that provides afunction and/or a process. Software 235 is also intended to includefirmware, middleware, microcode, hardware description language (HDL),and/or other form of instruction. By way of example, when device 200 isa companion device 140, software 235 may include a local profile agentfrom a third-party and a service provider application from the serviceprovider of service network 120. As another example, when device 200 isa primary device 150, software 235 may include a companion applicationfrom the third party and service provider activation application fromthe service provider of service network 120.

Input component 240 may include a mechanism that permits a user to inputinformation to device 200, such as a keyboard, a keypad, a button, aswitch, touch screen, etc. Output component 250 may include a mechanismthat outputs information to the user, such as a display, a speaker, oneor more light emitting diodes (LEDs), etc.

Communication interface 260 may include a transceiver that enablesdevice 200 to communicate with other devices and/or systems via wirelesscommunications, wired communications, or a combination of wireless andwired communications. For example, communication interface 260 mayinclude mechanisms for communicating with another device or system via anetwork. Communication interface 260 may include an antenna assembly fortransmission and/or reception of RF signals. For example, communicationinterface 260 may include one or more antennas to transmit and/orreceive RF signals over the air. For example, when device 200 is aprimary device 150, communication interface 260 may receive local RFsignals over the air from, and transmit RF signals over the air to,companion device 140. In one implementation, for example, communicationinterface 260 may communicate with a network and/or devices connected toa network. For example, when device 200 is a companion device 140,communication interface 260 may communicate with peripheral devices(such as push button, thermal sensor, etc.) to receive activity event orcollect data. Alternatively or additionally, communication interface 260may be a logical component that includes input and output ports, inputand output systems, and/or other input and output components thatfacilitate the transmission of data to other devices.

Secure Element (SE) 270 may be embedded within a secure elementinterface (e.g., a SIM card interface) of companion device 140 orprimary device 150. SE 270 may store secure applications and data topermit companion device 140 or primary device 150 to perform secureexchanges with other network entities. SE 270 provides the security andconfidentiality required to perform validation of a user's identity foraccess to core network 110, and/or support trusted exchanges amongvarious network entitles in networking environment 100. In oneembodiment, SE 270 may be permanently coupled to companion device 140,and thus cannot be removed by a user. According to one implementationfor companion device 140, SE 270 may include an eUICC that can beremotely provisioned.

Device 200 may perform certain operations in response to processor 220executing software instructions (e.g., software 235) contained in acomputer-readable medium, such as memory 230. A computer-readable mediummay be defined as a non-transitory memory device. A non-transitorymemory device may include memory space within a single physical memorydevice or spread across multiple physical memory devices. The softwareinstructions may be read into memory 230 from another computer-readablemedium or from another device. The software instructions contained inmemory 230 may cause processor 220 to perform processes describedherein. Alternatively, hardwired circuitry may be used in place of or incombination with software instructions to implement processes describedherein. Thus, implementations described herein are not limited to anyspecific combination of hardware circuitry and software.

Device 200 may include fewer components, additional components,different components, and/or differently arranged components than thoseillustrated in FIG. 2. As an example, in some implementations, a displaymay not be included in device 200. As another example, device 200 mayinclude one or more switch fabrics instead of, or in addition to, bus210. Additionally, or alternatively, one or more components of device200 may perform one or more tasks described as being performed by one ormore other components of device 200.

FIG. 3 is a diagram of functional components of companion device 140.The functional components of FIG. 3 may be implemented, for example, byprocessor 220 in conjunction with memory 230/software 235. As shown inFIG. 3, companion device 140 may include a service provider application310 and a local profile agent 320 within a local operating system 330(e.g., an embedded OS, etc.).

Service provider application 310 may include instructions to facilitateself-serve personalization and remote provisioning of companion device140. Service provider application 310 may interface with otherapplications and functions, such as local profile agent 320 andoperating system 330, to collect and provide user/account informationused to activate or update a line of service for companion device 140.Service provider application 310 may include personalization andconfiguration settings for an end-user associated with companion device140 and primary device 150. For example, service provider application310 may include an indication of a user's account standing as an accountowner or account member, which may have different account privileges.Service provider application 310 may also include or be able toautomatically retrieve a mobile directory number (MDN) of a primarydevice. In some instances, service provider application 310 may beprovided as an initial version at factory configuration and then updatedupon an initial pairing between companion device 140 and primary device150.

Local profile agent 320 may perform operations to activate and/or updatea SIM profile. Local profile agent 320 may respond to instructions fromservice provider application 310 to send an activation code, provide aneUICC identifier, and provide eUICC profile information. Local profileagent 320 may download a SIM profile, perform modem reset, and initiatedevice activation to activate companion device 140 on a carrier network.

Operating system 330 may include logic to manage functions of companiondevice 140. For example, in one implementation, operating system 330 mayinclude logic to collect and provide data from internal sensors orperipheral sensors associated with companion device 140. Operatingsystem 330 may rely on wireless communications, and particularlycellular communications using access network 105, to perform somefunctions. In one implementation, operating system 330 may beimplemented as a real-time operating system (RTOS). Operating system 330may also receive and store configuration settings, user profiles, andother user input to manage operation of companion device 140. Forexample, operating system 330 may store or access an internationalmobile equipment identity (IMEI) for companion device 140.

FIG. 4 is a block diagram illustrating an exemplary functional componentof primary device 150. The functional components of FIG. 4 may beimplemented, for example, by processor 220 in conjunction with memory230/software 235. In another implementation, some functional componentsof FIG. 4 may be implemented via a web browser interface in conjunctionwith partner server 160 or provider network 120. As shown in FIG. 4,primary device 150 may include a companion application 405 including alocal pairing function 410, and a service provider activationapplication 420.

Companion application 405 may generally include an application to managesettings for companion device 140. Companion application 405 may providean interface to allow a user to configure different settings forcompanion device 140. In one implementation, companion application 405may include a setup module for an initial configuration of companiondevice 140. The setup module may include a call to service providerapplication 310 to initiate cellular service activation for companiondevice 140. In other implementations, companion application 405 mayprovide additional features (not shown) such as monitoring, sharingdata, providing alerts, etc.

Local pairing function 410 may initiate a local wireless connectionbetween primary device 150 and companion device 140. In oneimplementation, local pairing function may include instructions toinitiate the local wireless connection in response to user input toprimary device 150 for an initial setup or activation.

Service provider activation application 420 may facilitate subscriptionmanagement for companion device 140 and may pass parameters to performactivation of companion device 140 to/from RPS 122. In oneimplementation, service provider activation application 420 may includesome or all features of service provider application 310, includingpersonal user information, such as an MDN of primary device 150 and anaccount standing (e.g., owner, member, etc.) of the end-user associatedwith primary device 150.

FIG. 5 is a diagram of exemplary communications among devices in aportion 500 of network environment 100. Communications in FIG. 5 mayrepresent communications for activating cellular service for a companiondevice with assistance from a primary device. As shown in FIG. 5,network portion 500 may include RPS 122, subscription manager platform124, provisioning platform 126, companion device 140, and primary device150. RPS 122, subscription manager platform 124, provisioning platform126, companion device 140, and primary device 150 may include featuresdescribed above in connection with FIGS. 1-4.

Companion device 140 may pair with primary device 150 in step S1. Forexample, an end user may launch local pairing function 410 (e.g., anAndroid® Wear app, a Samsung® Wear app, etc.) on primary device 150 thatcauses primary device to initiate a pairing of companion device 140 andthe primary device 150 over a local wireless connection (e.g., usingBT/BTE). Local pairing function 410 may hand off to SP activationapplication 420 to perform a personalization sequence. As part of thepersonalization sequence, SP activation application 420 on primarydevice 150 captures an EUICC ID (EID)/IMEI from companion device 140.

In step S2, SP activation application 420 provides the EID/IMEI to RPS122 using, for example, a wireless connection and an address for RPS 122provided in SP activation application 420.

In step S3, RPS 122 may request reservation, by subscription managerplatform 124, of a profile for the specific EID of step S2 (e.g., theEID of companion device 140). RPS 122 may be used as an eUICCpersonalization gateway and may support interfaces with subscriptionmanager platform 124. For the provided EID, subscription managerplatform 124 reserves an integrated circuit card identifier (ICCID)(e.g., a binding process) for the specified reservation request. TheICCID corresponds to a binary image file, which will be later downloadedto eUICC 330. Subscription manager platform 124 may provide the ICCID toRSP 122.

In step S4, RPS 122 may create a wireless service provisioning request,which is sent to provisioning platform 126 for distribution to billingservers and other network elements, for example, in core network 110.

At step S5, RSP 122 may construct a matching ID based on the MDN ofcompanion device 140 and a unique transaction number. At step S6, RSP122 may send a download profile request, including the ICCID and thematching ID, to subscription manager platform 124. Subscription managerplatform 124 may, in response, return the acknowledged ICCID to RSP 122.

At step S7, RSP 122 creates an activation code based on the matching IDfor companion device 140 and a fully qualified domain name (FQDN) ofsubscription manager platform 124. In step S8, RSP 122 may send theactivation code for companion device 140 to SP activation application420 on primary device 150. At step S9, primary device 150 may forwardthe activation code to service provider application 310 on companiondevice 140, using the paired BT connection.

At step S10, service provider application 310 on companion device 140may send the activation code to local profile agent 320 on companiondevice 140. As step S11, local profile agent 320 may initiate aconnection to subscription manager platform 124 (e.g., using the FQDNfrom the activation code) and download the profile with thecorresponding activation code.

At step S12, local profile agent 320 receives the profile, resets themodem (e.g., the LTE modem) of companion device 140, and companiondevice 140 is able to activate on the service provider network. In stepS13, subscription manager platform 124 may confirm successful downloadto RSP 122. In response, at step S14, RSP 122 may perform inventoryupdate functions with provisioning platform 126.

FIG. 6 is a flow diagram illustrating an exemplary process 600 forprovisioning an eUICC of a companion device for cellular activationaccording to an implementation described herein. In one implementation,process 600 may be performed by companion device 140 and primary device150. In another implementation, some or all of process 600 may beperformed by companion device 140 or primary device 150 along withanother device or group of devices in network environment 100.

As shown in FIG. 6, process 600 may include receiving user input toinitiate a cellular service activation process for a companion device(block 605), establishing a local wireless connection between a primaryuser device and the companion device (block 610), and providing to thecompanion device an updated activation application for cellular serviceactivation, where an updated activation application is available (block615). For example, a user may download to their primary device 150 acompanion application (e.g., companion application 405) for companiondevice 140. The companion application may include local pairing function410 to initiate a local wireless connection, between primary device 150and companion device 140, in response to user input on primary device150. Once paired, in one implementation, companion application 405 mayautomatically (e.g., without additional user input) initiate an updateof service provider application 310. Service provider application 310may include some or all features of service provider activationapplication 420, including personal user information, such as an MDN ofprimary device 150 and an account standing (e.g., owner, member, etc.)of the end-user associated with primary device 150.

Process 600 may also include sending from the companion device to theprimary device, via the local wireless connection, an eUICC identifierfor the companion device (block 620), and forwarding the eUICCidentifier from the primary device to a remote personalization server(block 625). For example, service provider application 310 on companiondevice 140 may obtain the eUICC identifier from local profile agent 320and provide the eUICC identifier to service provider activationapplication 420 on primary device 150. Primary device 150 may receivethe eUICC identifier via the local wireless connection and may forwardthe eUICC identifier with other identification for primary device 150 toRPS 122.

Process 600 may further include associating the companion device with asubscriber account for the primary device (block 630), and verifyingthat cellular service for the companion device can be provisioned underthe subscriber account (block 635). For example, RPS 122 may receive theeUICC identifier of companion device 140 and MDN (or other identifier)of primary device 150. RPS 122 may verify, for example, that the userassociated with primary device 150 is authorized to add a new line ofservice for the account associated with primary device 150, whetherother companion devices are already associated with the primary device150, that the account is in good standing, etc.

Process 600 may additionally include sending to the primary user devicean activation code for the eUICC of the companion device (block 640),forwarding the activation code to the activation application of thecompanion device via the local wireless connection (block 645). Forexample, RPS 122 may generate an activation code for companion device140 and send it to primary device 150. Primary device 150 may receivethe activation code and forward the activation code to service providerapplication 310 on companion device 140 via the local wireless pairing.

Process 600 may also include sending the activation code from theactivation application to a local profile agent of the companion device(block 650), and sending by the local profile agent of the companiondevice a profile request using the activation code (block 655). Forexample, once received from primary device 150, service providerapplication 310 may forward the activation code to local profile agent320. Local profile agent 320 may use the activation code to generate aSIM profile request that can be sent directly to subscription managerplatform 124 (e.g., without relying on primary device 150). Thus,companion device 140 can be personalized and provisioned using aself-serve process with minimal user input to either companion device140 or primary device 150.

FIG. 7 provides an illustration of a use case for end-user interactionsduring a first time synchronization of companion device 140 with primarydevice 150, according to an implementation. In the example of FIG. 7,assume primary device 150 includes a third-party application (e.g.,Android® Wear, Samsung® Wear, etc.) for interacting with companiondevice 140 and for pairing with companion device 140 (e.g., shown inFIG. 7 as a smart watch). Also, companion device 140 is provided with aneUICC that has no SIM profile.

A user (e.g., end-customer) turns on companion device 140. Local profileagent 320 on the companion device 140 helps the primary device 150 andthe companion device 140 to get paired 705 via a Bluetooth® connectionor another short range wireless interface. In another implementation,companion device 140 and primary device 150 may be paired over a wiredinterface.

Companion device 140 may have a preloaded version of the serviceprovider application (e.g., service provider application 310). Whencompanion device 140 and primary device 150 are paired, a packagereplacement 710 of service provider application 310 follows (i.e.,service provider application 310 on companion device 140 is replaced byservice provider activation application 420 on primary device 150). Apackage replace intent is sent from the local pairing function 410(e.g., the Android framework) and service provider activationapplication 420 listens to this intent to identify that pairing is nowcomplete.

Service provider application 310 then queries 715 local profile agent320 on companion device 140 to get the SIM profile information if aprofile is available. For example, service provider application 310 mayhave exchanges with local profile agent 320 such as “Query EID” or“Query Profile.” In one implementation, queries 715 may also include aquery IMEI to operating system 330 to obtain the IMEI for companiondevice 140. If not already provided through package replacement 710,service provider application 310 may also obtain 720 information fromprimary device 150, such as the primary device MDN, that will enablecompanion device 140 to be associated with primary device 150 forback-end queries.

Service provider application 310 then sends query 725, via primarydevice 150, to back end systems (e.g., server 122 in service network120) that are systems of record to identify the next steps to execute.Specific information from companion device 140 like the IMEI, ICCID, andEID are used when back end system is queried. Specific information fromprimary device 150 may also be used, such as the MDN of primary device150, an application version of service provider activation application420, etc. The back-end systems may determine, for example, based on thesubscriber's records, that companion device 140 is eligible for a newline of service or that companion device 140 may be a device upgrade(e.g., a replacement device for an existing line of service). Thisdetermination may be indicated in response 730 provided to companiondevice 140 via primary device 150. For example, if no companion deviceis associated with the MDN of primary device 150, companion device 140may be added as a new line of service. In response, companion device 140may display a specific notification called “Get Connected” 735. However,if other companion devices are associated with the MDN of primary device150, companion device 140 may be used to upgrade an existing device onthe account. In this scenario, a different notification (not shown),such as “Upgrade Device,” may be displayed with a presentation ofcompanion devices eligible to be upgraded. In one implementation,additional information 740 may be presented via primary device 150.

When service provider application 310 determines that companion device140 needs to be personalized, local profile agent 320 on companiondevice 140 may be utilized to download 745 the required SIM profiledirectly from service network 120. Service provider application 310 mayhave has interactions with local profile agent 320 like “Send ActivationCode,” “Register for download complete callback,” etc.

FIG. 8 provides an illustration of a use case for a subsequent reboot ofcompanion device 140 or synchronization of service provider application310, according to an implementation. Service provider application 310listens to events related to companion device 140 reboot and app sync.No package replace happens in this flow. On a reboot of companion device140 or app sync of the companion device 140 (e.g., after the first timeboot/app sync), service provider application 310 on companion device 140will repeat the interactions with local profile agent 320 and backendsystems in in core network 110 or service network 120 (e.g., references715, 725, 730 of FIG. 7).

The back-end systems may determine, for example, based on thesubscriber's records, that (1) companion device 140 has not beenactivated and is eligible for a new line of service; (2) companiondevice 140 has not been activated and may be a device upgrade; (3)companion device 140 is an already active device, but the profile wasdeleted from companion device 140; or (4) companion device 140 is analready active device, but the profile was disabled on companion device140. If any of options (1), (2), or (3) are determined, companion device140 may present the “Get Connected” option to the user, similar to thedescription of FIG. 7. However, if the profile was disabled on companiondevice 140 (option (4)), a specific notification called “Can't Connect”may be displayed on companion device 140. Using local connection 705,service provider application 310 may have service provider activationapplication 420 provide additional information 810 via primary device150.

FIG. 9 provides an illustration of a use case for another entry pointfor a user to initiate a personalization and provisioning process fromcompanion device 140, according to an implementation. In the use case ofFIG. 9, companion device 140 may initiate pairing and activation, incontrast to the primary device 150 activation initiation describedabove. In this example, an entry point or user option referred to as“Activate Watch” may be available to the user as an item from the listof all applications on companion device 140. This entry point may beseparate from the notifications (e.g., notification 735) previouslydescribed. When activate watch launcher 905 is selected, companiondevice 140 may initiate a local wireless pairing 910 with primary device150. Once paired, companion device 140 may retrieve updates and primarydevice 150 information to support exchanges with back end systems incore network 110 or service network 120, as described above inconnection with, for example, FIGS. 7 and 8.

After a profile download is successfully performed, companion device 140may remove the “Activate Watch” launcher from the application list. On asubsequent reboot or app sync, if companion device 140 is found to benot active on the network, the launcher is then enabled again (e.g., aspart of package replacement 710 of service provider application 310).

FIG. 10 provides an illustration of a use case for restoring a deletedprofile from companion device 140, according to an implementation. Auser (e.g., end customer) may delete the profile downloaded on companiondevice 140 intentionally or inadvertently. In such cases, companiondevice 140 may or may not be able to attach to the carrier network. Afew different use cases can arise. In one instance, there may be noprofile on companion device 140, and companion device 140 has an activeline of service on an account. The same account user as before wants tore-activate this watch. In another instance, there may be no profile oncompanion device 140, and companion device 140 has an active line ofservice on an account. But a different account user wants to activatecompanion device 140. In still another instance, there may be no profileon companion device 140 and no active line of service on any account.

As shown in the process flow of FIG. 10, service provider application310 on companion device 140 may interact with local profile agent 320 toquery EID and query Profile (block 1005, corresponding, e.g., toreference 715 of FIG. 7). Service provider application 310 may alsointeract with the companion device OS 330 to query the IMEI of companiondevice 140 (block 1010, also corresponding, e.g., to reference 715 ofFIG. 7). Service provider application 310 may interact with backendsystems in core network 110 or service network 120 to determine if theIMEI stored in OS 330 is present on the account of primary device 150(block 1015, corresponding, e.g., to reference 725 and 730 of FIG. 7).

If the IMEI of companion device is present on the account of primarydevice 150 (block 1020—Yes), service provider application 310 mayinitiate procedures to personalize companion device 140 and provisioncompanion device 140 with the already associated line of service on theexisting account of primary device 150 (block 1025). If the IMEI is notpresent on the account of primary device 150 (block 1020—No), serviceprovider application 310 may personalize companion device 140 andprovision companion device 140 with a new line of service on the accountof paired primary device 150 (block 1025). In one implementation (e.g.,if companion device 140 had an active line of service on anotheraccount), the back end provisioning may include deactivating the linefor companion device 140 associated with the previous account.

FIG. 11 provides an illustration of a use case for end-user interactionsduring a first time synchronization of companion device 140 with primarydevice 150, according to an implementation. In the example of FIG. 11,assume the end-user of primary device 150 is an account member withoutauthorization to add services to the account (e.g., in contrast with anaccount owner, such as would be the case in the example of FIG. 7).

As shown in FIG. 11, an activation process may include pairing 705,package replacement 710, and queries 715 as described above inconnection with FIG. 7. When query 715 indicates that the end-user ofprimary device 150 is an account member without authorization to addservices to the account, service provider application 310 may presentoptions 1105 to the user including (1) notify the account owner and (2)sign in as the account owner. In one implementation, using localconnection 705, service provider application 310 may have serviceprovider activation application 420 provide additional information 1110via primary device 150.

If a user selects an option from options 1105 to notify the accountowner, service provider application 310 or service provider activationapplication 420 may automatically send a text message (e.g., and SMS oranother type of message) to the account owner. For example, primarydevice 150 of the account member can send a text message 1115 (e.g., inreal time) to the account owner to get approval for adding companiondevice 140 to the account. The account owner can approve. This approvalmay be relayed back to the account member via a push notification 1120which says “owner has approved.” The push notification may be relayed1125 to companion device 140. The account member can then initiate theprocess of personalization and provisioning as described above inconnection with FIG. 7 (e.g., reference 725 and following).

If a user selects an option from options 1105 to sign in as the accountowner, the account member can request the account owner to sign in onthe account member's primary device 150. Once the sign in is successful,the personalization/provisioning process can execute on the Smartphoneas described above in connection with FIG. 7.

According to implementations described herein, association of userinformation from primary device 150 and device information fromcompanion device 140 facilitates self-serve personalization and remoteprovisioning of the eUICC for companion device 140. In someimplementations, detection of a SIM profile and/or obtaining a new SIMprofile from companion device 140 may be performed in a manner that istransparent to the user after an initial authorization by chainingmultiple authorization steps using service provider application 310 andservice provider activation application 420. Use of primary devicesystems and methods described herein may also enable a manufacture ofcompanion device 140 to provide a single device for a global platform,allowing a local SIM profile (e.g., for service providers of aparticular country or continent) to be obtained upon device activation.

Systems and methods described herein enable an end user to self-serveactivate for cellular service of an eUICC companion device via a networkconnection to a primary device with intuitive minimal user input withoutrequiring any specific companion device information to be entered, suchas IMEI, EID, ICCID, or activation QR code or similar code.Additionally, the systems and methods provide a solution for a situationwhere re-personalization of eUICC profile is required to restorecellular service of a companion device due to an event where afunctioning user profile is missing or damaged, regardless of whether acompanion device has a pre-installed eUICC with a pre-personalized eUICCprofile.

In the preceding specification, various preferred embodiments have beendescribed with reference to the accompanying drawings. Variousmodifications and changes may be made thereto, and additionalembodiments may be implemented, without departing from the broader scopeof the invention as set forth in the claims that follow. Thespecification and drawings are accordingly to be regarded in anillustrative rather than restrictive sense. For example, while series ofblocks have been described with respect to FIGS. 6 and 10, the order ofthe blocks may be modified in other implementations. Further,non-dependent blocks may be performed in parallel.

Different aspects of the description provided above may be implementedin many different forms of software, firmware, and hardware in theimplementations illustrated in the figures. The actual software code orspecialized control hardware used to implement these aspects is notlimiting of the invention. Thus, the operation and behavior of theseaspects were described without reference to the specific softwarecode—it being understood that software and control hardware can bedesigned to implement these aspects based on the description herein.

Further, certain portions of the invention may be implemented as a“component” or “system” that performs one or more functions. Thesecomponents/systems may include hardware, such as a processor, an ASIC,or a FPGA, or a combination of hardware and software.

To the extent the aforementioned embodiments collect, store or employpersonal information provided by individuals, it should be understoodthat such information shall be used in accordance with all applicablelaws concerning protection of personal information. Additionally, thecollection, storage and use of such information may be subject toconsent of the individual to such activity, for example, through wellknown “opt-in” or “opt-out” processes as may be appropriate for thesituation and type of information. Storage and use of personalinformation may be in an appropriately secure manner reflective of thetype of information, for example, through various encryption andanonymization techniques for particularly sensitive information.

No element, act, or instruction used in the present application shouldbe construed as critical or essential to the invention unless explicitlydescribed as such. Also, as used herein, the article “a” and “one of” isintended to include one or more items. Further, the phrase “based on” isintended to mean “based, at least in part, on” unless explicitly statedotherwise.

What is claimed is:
 1. A method, comprising: receiving, by a primaryuser device, input to initiate a cellular service activation process fora companion device, wherein the companion device includes a preloadedversion of a service provider application for facilitating remoteprovisioning; providing, by the primary user device and to the companiondevice, an updated version of the service provider application thatreplaces the preloaded version; receiving, by the primary user device,and from the companion device, an embedded universal integrated circuitcard (eUICC) identifier for the companion device; forwarding, by theprimary user device and to a network device in a service providernetwork, the eUICC identifier and an identifier for the primary userdevice; and when the network device verifies that the cellular serviceactivation for the companion device can be provisioned under asubscriber account: receiving, by the primary user device and from thenetwork device, an activation code for the companion device to use toinitiate a request for a new line of service for the eUICC identifier;and forwarding, by the primary user device and to the companion device,the activation code.
 2. The method of claim 1, further comprising:establishing, by the primary user device, a local wireless networkconnection with the companion device.
 3. The method of claim 1, whereinforwarding the eUICC identifier and an identifier for the primary userdevice comprises: forwarding data indicating an account standing of auser associated with the primary user device.
 4. The method of claim 1,wherein receiving the eUICC identifier further comprises receiving aninternational mobile equipment identity (IMEI) for the companion device.5. The method of claim 1, wherein the identifier of the primary userdevice includes a mobile directory number (MDN).
 6. The method of claim1, wherein the activation code includes information for the companiondevice to download a subscriber identity module (SIM) profile.
 7. Themethod of claim 1, wherein providing the updated version of the serviceprovider application further comprises: providing the updated version ofthe service provider application via a local wireless interface.
 8. Themethod of claim 1, further comprising: when the network device does notverify that the cellular service for the companion device can beprovisioned under the subscriber account: presenting, by the primaryuser device and to a user, additional information to supplement a queryby the companion device.
 9. The method of claim 1, wherein providing theupdated version of the service provider application includes providingthe updated version of the service provider application to a wearabledevice or an embedded device.
 10. The method of claim 1, furthercomprising: determining that a user of the primary user device is notauthorized to add a line of service to the subscriber account;determining that the user of the primary user device requiresauthorization from an owner of the account; and automatically generatinga message to send to the account owner when the user of the primary userdevice requires authorization.
 11. A user device, comprising: a networkinterface with a transceiver to communicate with one or more remotedevices: an input component; one or more memories storing an activationapplication for cellular service activation of a companion device; and aprocessor to execute instructions in the activation application to:receive input to initiate a cellular service activation process for thecompanion device, wherein the companion device includes a preloadedversion of a service provider application for facilitating remoteprovisioning, provide, to the companion device, an updated version ofthe service provider application that replaces the preloaded version;receive, from the companion device, an embedded universal integratedcircuit card (eUICC) identifier for the companion device; forward, to anetwork device in a service provider network, the eUICC identifier andan identifier for the user device, and when the network device verifiesthat the cellular service activation for the companion device can beprovisioned under a subscriber account: receive, from the networkdevice, an activation code for the companion device to use to initiate arequest for a new line of service for the eUICC identifier; and forwardthe activation code to the companion device.
 12. The user device ofclaim 11, wherein the processor is further to execute instructions inthe activation application to: establish a local wireless networkconnection with the companion device.
 13. The user device of claim 11,wherein, when forwarding the eUICC identifier and an identifier for theuser device, the processor is further to execute instructions in theactivation application to: forward data indicating an account standingof a user associated with the user device.
 14. The user device of claim11, wherein, when receiving the eUICC identifier, the processor isfurther to execute instructions in the activation application to:receive an associated international mobile equipment identity (IMEI) forthe companion device.
 15. The user device of claim 11, wherein, whenforwarding the activation code, the processor is further to executeinstructions in the activation application to: forward information forthe companion device to download a subscriber identity module (SIM)profile.
 16. The user device of claim 11, wherein the processor isfurther to execute instructions in the activation application to:determine that a user of the user device is not authorized to add a lineof service to the subscriber account; confirm that the user wants torequest authorization from an owner of the subscriber account; andautomatically generate a message to the account owner when the userwants to request authorization.
 17. The user device of claim 11, whereinthe user device includes a smart phone, and wherein the companion deviceincludes a wearable device.
 18. A non-transitory computer-readablemedium storing instructions executable by a computational device to:receive input to initiate a cellular service activation process for acompanion device, wherein the companion device includes a preloadedversion of a service provider application for facilitating remoteprovisioning, provide, to the companion device, an updated version ofthe service provider application that replaces the preloaded version;receive, from the companion device, an embedded universal integratedcircuit card (eUICC) identifier for the companion device; forward, to anetwork device in a service provider network, the eUICC identifier andan identifier for a primary user device, and when the network deviceverifies that the cellular service activation for the companion devicecan be provisioned under a subscriber account: receive, from the networkdevice, an activation code for the companion device to use to initiate arequest for a new line of service for the eUICC identifier; and forwardthe activation code to the companion device.
 19. The non-transitorycomputer-readable medium of claim 18, wherein the instructions toforward the eUICC identifier further comprise instructions to: forwardan international mobile equipment identity (IMEI) for the companiondevice.
 20. The non-transitory computer-readable medium of claim 18,further comprising instructions to: determine that a user of the primaryuser device is not authorized to add a line of service to the subscriberaccount; request the user to sign in as an owner of the subscriberaccount; and receive the activation code when the user signs in as theowner of the account.